The weekly review: 30 minutes that steer everything

A weekly review is a fixed 30-minute appointment — same day, same time — where you close the finished week and set up the next one: what shipped, what dragged, what the numbers say, and what the one priority is for the coming five days. It is the control loop of a personal operating system: without it, every other habit drifts, because nothing is checking whether the habits still point at the right work.

Everything else in my personal operating system — focus blocks, decision rules, capture habits — is steered from this half hour. It is the only meeting I have never been tempted to cancel, because it is the meeting that decides all the others.

Why does a business drift without one?

Because weeks are reactive by default. Client requests, inbox threads and small fires allocate your time for you, and each individual allocation looks reasonable. The drift only becomes visible over months: the quarter ends, the important project has not moved, and nobody can say quite where the time went.

A review is the mechanism that interrupts this. It creates one moment per week where the question is not "what is urgent?" but "is this still the right direction?" Thirty minutes is enough, because the review's job is steering, not doing. Reviews that swell to two hours become dreaded, and dreaded reviews die within six weeks.

What is the agenda?

Mine has five parts, roughly six minutes each:

1. Close the week. List what actually shipped. Not what was worked on — what finished.
2. Read the friction log. Tally repeats; promote anything that has appeared three times to the fix list.
3. Check the numbers. Three to five personal and business metrics, 60 seconds each. For me: proposals out, pipeline conversations, content shipped, focus blocks kept.
4. Sweep the loose ends. Empty capture points — notes, flagged emails, open browser tabs — into either the task list or the bin.
5. Set the week. One primary priority, then pre-assign each day's two-hour execution block so no morning starts with a decision.

The order matters: evidence first (what shipped, what dragged, what the numbers say), decisions last. Reviews that start with planning skip the uncomfortable part, and the uncomfortable part is the point.

How does the review actually steer?

Through explicit if-then rules, so the same evidence always produces a response. When something ships, then it gets crossed off and the next piece of that project is named. When the friction log shows a repeat, then a fix is scheduled — not noted, scheduled. When a metric is below its floor for two consecutive weeks, then the coming week's priority changes to address it, whatever else was planned. When the loose-end sweep turns up a commitment I no longer intend to keep, then I write the closing email in the review itself rather than carrying the guilt another week.

The rules remove negotiation. A review without consequences is journalling; pleasant, but it steers nothing.

What kills weekly reviews, and how do you keep yours alive?

Three things kill them: length, vagueness and shame. Length is solved by the 30-minute cap and a written agenda. Vagueness is solved by the five fixed sections — you are never wondering what to do next. Shame is the quiet one: after a bad week, the review feels like an appointment with your own failure, so you skip it, and then the system is gone. The fix is a standing rule that the review is diagnostic, not evaluative. A bad week reviewed is data; a bad week skipped is a habit forming. My other rule: the review may be moved within 48 hours but never cancelled — the same repair standard I apply to focus blocks. And perfectionists should note the review is also where ship-at-80% rules get enforced: if something has been "nearly done" for two consecutive reviews, it ships this week or gets killed.

Does this scale beyond one person?

Yes — the same loop runs a firm. A weekly numbers-and-priorities review is the smallest management system I install with clients, and the sector-by-sector patterns in our growth systems by industry map all assume one exists: same agenda shape, same evidence-before-decisions order, pipeline numbers instead of personal ones. Founders who cannot run a 30-minute review for themselves rarely run one for their business.

Book it now: Friday afternoon or Monday morning, 30 minutes, recurring. Run it badly for four weeks. A mediocre review that happens weekly will out-steer a perfect system that exists only in your head.

---

Keep the thinking coming: The Format — a fortnightly letter on business and personal systems. Subscribe by email.